Predictive maintenance of optical transport network system

ABSTRACT

A system for predictive maintenance of at least one optical network element in an optical transport network including a power monitor in communication with the at least one optical network element, the power monitor configured to selectively retrieve an actual power level from the optical network element; the power monitor being in communication with a data store having a specified power level for each of the at least one optical network element and an acceptable tolerance, wherein the specified power level includes a low mark and a high mark defining a specified power level range; wherein the power monitor compares the actual power level to the specified power level; and generates a signal if the actual power level is outside of the specified power level range by an amount greater than the acceptable tolerance.

TECHNICAL FIELD

This disclosure relates generally to network management and, morespecifically, to assigning and configuring general purpose hardware tosupport virtual network functions. Most specifically, the disclosurerelates to retrieving optical power levels of network elements andcomparing minimum, maximum and average power levels for each element toassess performance levels for maintenance.

BACKGROUND

Communication networks have migrated from using specialized networkingequipment executing on dedicated hardware, like routers, firewalls, andgateways, to software defined networks (SDNs) executing as virtualizednetwork functions (VNF) in a cloud infrastructure. To provide a service,a set of VNFs may be instantiated on the general purpose hardware. EachVNF may require one or more virtual machines (VMs) to be instantiated.In turn, VMs may require various resources, such as memory, virtualcomputer processing units (vCPUs), and network interfaces or networkinterface cards (NICs). Determining how to assign these resources amongVMs in an efficient manner may be unbearably complex.

This disclosure is directed to solving one or more of the problems inthe existing technology.

SUMMARY

A system for predictive maintenance of at least one optical networkelement in an optical transport network according to one examplecomprises a power monitor in communication with the at least one opticalnetwork element, the power monitor configured to selectively retrieve anactual power level from the optical network element; the power monitorbeing in communication with a data store having a specified power levelfor each of the at least one optical network element and an acceptabletolerance, wherein the specified power level includes a low mark and ahigh mark defining a specified power level range; wherein the powermonitor compares the actual power level to the specified power level;and generates a signal if the actual power level is outside of thespecified power level range by an amount greater than the acceptabletolerance.

According to another example, the disclosure provides a system forpredictive maintenance of an optical transport network, the systemcomprising plural optical network elements in the optical transportnetwork, each optical network element operating at an actual powerlevel; at least one data store having a specified power level for eachoptical network element, wherein the specified power level includes alow mark and a high mark defining a specified power level range; a powermonitor in communication with the data store and the optical networkelements, the power monitor configured to selectively communicate witheach optical network element according to a schedule, to retrieve theactual power level and store the actual power level in a memory, thepower monitor is further configured to compare the actual power level tothe specified power level, and wherein the power monitor is configuredto generate a first signal upon detecting that the actual power levelfor at least one of the plural optical network elements is within anacceptable tolerance of the low mark or high mark, and wherein the powermonitor is configured to generate a second signal upon detecting theactual power level for at least one of the plural optical networkelements is outside of specified power level range.

BRIEF DESCRIPTION OF THE DRAWINGS

In the following description, for purposes of explanation, numerousspecific details are set forth in order to provide an understanding ofthe variations in implementing the disclosed technology. However, theinstant disclosure may take many different forms and should not beconstrued as limited to the examples set forth herein. Where practical,like numbers refer to like elements throughout.

FIG. 1a is a representation of an exemplary network.

FIG. 1b is a representation of an exemplary hardware platform.

FIG. 2 is a representation of an optical transport network maintenancesystem according to an example.

FIG. 2a is a flow chart depicting operation of an optical transportnetwork maintenance system according to one example.

FIG. 2b is a representation depicting a graphical user interface for anoptical transport network maintenance system according to one example.

FIG. 2c is a flow chart and schematic depiction of operation of anoptical transport network maintenance system according to one example.

FIG. 3 is a representation of a network device according to an example.

FIG. 4 depicts an exemplary communication system that provide wirelesstelecommunication services over wireless communication networks that maybe at least partially implemented as an SDN.

FIG. 5 depicts an exemplary diagrammatic representation of a machine inthe form of a computer system.

FIG. 6 is a representation of a telecommunications network.

FIG. 7 is a representation of a core network.

FIG. 8 is a representation packet-based mobile cellular networkenvironment.

FIG. 9 is a representation of a GPRS network.

FIG. 10 is a representation a PLMN architecture.

DETAILED DESCRIPTION

Service providers continue to deploy optical transport network (OTN)with the goal of boosting bandwidth and increasing networkfunctionality. OTN supports different traffic types in a morecost-effective manner than by using SONET/SDH networks. Carriers areplacing particular emphasis on OTN in metro areas, where they areshifting rapidly from SONET/SDH to Dense Wavelength-DivisionMultiplexing (DWDM). With mounting data traffic on their networks,service providers today face a decision about how to use OTN. Carriersfall into three groups: 1) Some are looking at putting Internet Protocol(IP) traffic into OTN and then multiplex the OTN into DWDM; 2) Otherswant to use IP over DWDM, because most of their traffic is IP; 3) Somemajor carriers want to use OTN only for legacy time-divisionmultiplexing (TDM) traffic, but will use packet interfaces for their IPtraffic. As the transport networks are being transformed into opticaltransport network, it is extremely critical to routinely monitor opticalnetwork elements (ONE), such as, cards, ports or other elements thatrely on optical emitters, such as, lasers to transport data across thenetwork for any possible degradation of optical power levels. Suchdegradation and failure is one of the major issues relating to thehealth of OTNs. Degradation of laser and optical power levels canintroduce digital performance monitoring (PM) errors causing loss ofpackets over the network requiring retries, which in the end lead toLayer1/Layer2/Layer3 service not meeting previously agreed to servicelevel agreements (SLAs). According to the examples described herein, asystem for predictive maintenance of optical network elements isprovided, which on a routine basis retrieves an optical power level, orsimply power level, of the optical network elements in the network andcompares the maximum, minimum and average power levels at element. Thenthe system compares those actual retrieved values against the high andlow water marks provided by the vendor of the network element. If theactual retrieved values are either not within the high and low watermarks or are inside a tolerance required for error free transmission(acceptable tolerance), a work trouble ticket is generated to repair orreplace the affected network element. This allows repair or replacementof ONEs before they start either causing high digital PM errors or ahard failure helping service providers to meet previously agreed to SLAswith all customers. The system described in the examples below may beimplemented in any network that contains optical network elementsincluding but not limited to the several example networks describedherein. An optical network according to the examples herein, is anynetwork that includes at least on optical network element.

FIG. 1a is a representation of an exemplary network 100. Network 100 maycomprise an SDN—that is, network 100 may include one or more virtualizedfunctions implemented on general purpose hardware, such as in lieu ofhaving dedicated hardware for every network function. That is, generalpurpose hardware of network 100 may be configured to run virtual networkelements to support communication services, such as mobility services,including consumer services and enterprise services. These services maybe provided or measured in sessions.

A virtual network function(s) (VNF) 102 may be able to support a limitednumber of sessions. Each VNF 102 may have a VNF type that indicates itsfunctionality or role. For example, FIG. 1a illustrates a gateway VNF102 a and a policy and charging rules function (PCRF) VNF 102 b.Additionally or alternatively, VNFs 102 may include other types of VNFs.Each VNF 102 may use one or more virtual machine (VM) 104 to operate.Each VM 104 may have a VM type that indicates its functionality or role.For example, FIG. 1a illustrates a management control module (MCM)VM 104a and an advanced services module (ASM) VM 104 b. Additionally oralternatively, VM 104 may include other types of VMs. Each VM 104 mayconsume various network resources from a hardware platform 106, such asa resource 108, a virtual central processing unit (vCPU) 108 a, memory108 b, or a network interface card (NIC) 108 c. Additionally oralternatively, hardware platform 106 may include other types ofresources 108.

While FIG. 1a illustrates resources 108 as collectively contained inhardware platform 106, the configuration of hardware platform 106 mayisolate, for example, certain memory 108 c from other memory 108 c. FIG.1b provides an exemplary implementation of hardware platform 106.

Hardware platform 106 may comprise one or more chasses 110. Chassis 110may refer to the physical housing or platform for multiple servers orother network equipment. In an aspect, chassis 110 may also refer to theunderlying network equipment. Chassis 110 may include one or moreservers 112. Server 112 may comprise general purpose computer hardwareor a computer. In an aspect, chassis 110 may comprise a metal rack, andservers 112 of chassis 110 may comprise blade servers that arephysically mounted in or on chassis 110.

Each server 112 may include one or more network resources 108, asillustrated. Servers 112 may be communicatively coupled together (notshown) in any combination or arrangement. For example, all servers 112within a given chassis 110 may be communicatively coupled. As anotherexample, servers 112 in different chasses 110 may be communicativelycoupled. Additionally or alternatively, chasses 110 may becommunicatively coupled together (not shown) in any combination orarrangement.

The characteristics of each chassis 110 and each server 112 may differ.For example, FIG. 1b illustrates that the number of servers 112 withintwo chasses 110 may vary. Additionally or alternatively, the type ornumber of resources 110 within each server 112 may vary. In an aspect,chassis 110 may be used to group servers 112 with the same resourcecharacteristics. In another aspect, servers 112 within the same chassis110 may have different resource characteristics.

Given hardware platform 106, the number of sessions that may beinstantiated may vary depending upon how efficiently resources 108 areassigned to different VMs 104. For example, assignment of VMs 104 toparticular resources 108 may be constrained by one or more rules. Forexample, a first rule may require that resources 108 assigned to aparticular VM 104 be on the same server 112 or set of servers 112. Forexample, if VM 104 uses eight vCPUs 108 a, 1 GB of memory 108 b, and 2NICs 108 c, the rules may require that all of these resources 108 besourced from the same server 112. Additionally or alternatively, VM 104may require splitting resources 108 among multiple servers 112, but suchsplitting may need to conform with certain restrictions. For example,resources 108 for VM 104 may be able to be split between two servers112. Default rules may apply. For example, a default rule may requirethat all resources 108 for a given VM 104 must come from the same server112.

An affinity rule may restrict assignment of resources 108 for aparticular VM 104 (or a particular type of VM 104). For example, anaffinity rule may require that certain VMs 104 be instantiated on (thatis, consume resources from) the same server 112 or chassis 110. Forexample, if VNF 102 uses six MCM VMs 104 a, an affinity rule may dictatethat those six MCM VMs 104 a be instantiated on the same server 112 (orchassis 110). As another example, if VNF 102 uses MCM VMs 104 a, ASM VMs104 b, and a third type of VMs 104, an affinity rule may dictate that atleast the MCM VMs 104 a and the ASM VMs 104 b be instantiated on thesame server 112 (or chassis 110). Affinity rules may restrict assignmentof resources 108 based on the identity or type of resource 108, VNF 102,VM 104, chassis 110, server 112, or any combination thereof.

An anti-affinity rule may restrict assignment of resources 108 for aparticular VM 104 (or a particular type of VM 104). In contrast to anaffinity rule—which may require that certain VMs 104 be instantiated onthe same server 112 or chassis 110—an anti-affinity rule requires thatcertain VMs 104 be instantiated on different servers 112 (or differentchasses 110). For example, an anti-affinity rule may require that MCM VM104 a be instantiated on a particular server 112 that does not containany ASM VMs 104 b. As another example, an anti-affinity rule may requirethat MCM VMs 104 a for a first VNF 102 be instantiated on a differentserver 112 (or chassis 110) than MCM VMs 104 a for a second VNF 102.Anti-affinity rules may restrict assignment of resources 108 based onthe identity or type of resource 108, VNF 102, VM 104, chassis 110,server 112, or any combination thereof.

Within these constraints, resources 108 of hardware platform 106 may beassigned to be used to instantiate VMs 104, which in turn may be used toinstantiate VNFs 102, which in turn may be used to establish sessions.The different combinations for how such resources 108 may be assignedmay vary in complexity and efficiency. For example, differentassignments may have different limits of the number of sessions that canbe established given a particular hardware platform 106.

For example, consider a session that may require gateway VNF 102 a andPCRF VNF 102 b. Gateway VNF 102 a may require five VMs 104 instantiatedon the same server 112, and PCRF VNF 102 b may require two VMs 104instantiated on the same server 112. (Assume, for this example, that noaffinity or anti-affinity rules restrict whether VMs 104 for PCRF VNF102 b may or must be instantiated on the same or different server 112than VMs 104 for gateway VNF 102 a.) In this example, each of twoservers 112 may have sufficient resources 108 to support 10 VMs 104. Toimplement sessions using these two servers 112, first server 112 may beinstantiated with 10 VMs 104 to support two instantiations of gatewayVNF 102 a, and second server 112 may be instantiated with 9 VMs: fiveVMs 104 to support one instantiation of gateway VNF 102 a and four VMs104 to support two instantiations of PCRF VNF 102 b. This may leave theremaining resources 108 that could have supported the tenth VM 104 onsecond server 112 unused (and unusable for an instantiation of either agateway VNF 102 a or a PCRF VNF 102 b). Alternatively, first server 112may be instantiated with 10 VMs 104 for two instantiations of gatewayVNF 102 a and second server 112 may be instantiated with 10 VMs 104 forfive instantiations of PCRF VNF 102 b, using all available resources 108to maximize the number of VMs 104 instantiated.

Consider, further, how many sessions each gateway VNF 102 a and eachPCRF VNF 102 b may support. This may factor into which assignment ofresources 108 is more efficient. For example, consider if each gatewayVNF 102 a supports two million sessions, and if each PCRF VNF 102 bsupports three million sessions. For the first configuration—three totalgateway VNFs 102 a (which satisfy the gateway requirement for sixmillion sessions) and two total PCRF VNFs 102 b (which satisfy the PCRFrequirement for six million sessions)—would support a total of sixmillion sessions. For the second configuration—two total gateway VNFs102 a (which satisfy the gateway requirement for four million sessions)and five total PCRF VNFs 102 b (which satisfy the PCRF requirement for15 million sessions)—would support a total of four million sessions.Thus, while the first configuration may seem less efficient looking onlyat the number of available resources 108 used (as resources 108 for thetenth possible VM 104 are unused), the second configuration is actuallymore efficient from the perspective of being the configuration that cansupport more than the greater number of sessions.

To solve the problem of determining a capacity (or, number of sessions)that can be supported by a given hardware platform 105, a givenrequirement for VNFs 102 to support a session, a capacity for the numberof sessions each VNF 102 (e.g., of a certain type) can support, a givenrequirement for VMs 104 for each VNF 102 (e.g., of a certain type), agiven requirement for resources 108 to support each VM 104 (e.g., of acertain type), rules dictating the assignment of resources 108 to one ormore VMs 104 (e.g., affinity and anti-affinity rules), the chasses 110and servers 112 of hardware platform 106, and the individual resources108 of each chassis 110 or server 112 (e.g., of a certain type), aninteger programming problem may be formulated.

It will be understood that the various networks described hereinincluding the network described in connection with FIGS. 1a and 1b ,comprise network elements that rely on optical transport ofcommunications and signals. Such networks include optical networkelements that include optical emitters, such as lasers, that can degradein performance over time and require repair or replacement to restorethe element to appropriate service levels. Typically, degradation is notdetected until a network element fails or stops functioning properly.According to an example, an optical transport network predictivemaintenance system, generally indicated by the number 200 in FIG. 2 isprovided to improve the likelihood of detecting degradation in anoptical network element before PM loss or a hard failure.

System 200 generally includes a power monitor indicated by the number210. Power monitor 210 may be a standalone device or incorporated in anetwork device or a virtual machine. Power monitor 210 communicates withat least one optical network element, generally indicated by the number220. Optical network elements 220 include ports, cards and other networkelements that use an optical emitter 225, such as a laser or othersuitable optical device to transmit information across the network 230.With reference to FIG. 2, network 230 may include any number opticalnetwork elements 220 including for example a first optical networkelement 220 ₁, a second optical network element 220 ₂ through an nthoptical network element 220 _(N).

Power monitor 210 selectively communicates with the optical networkelements 220 to retrieve an actual power level for each optical emitter225. Power monitor 210 may be configured to retrieve actual power levelsfrom every optical network element on a selected network or portionthereof, or it may be configured to retrieve actual power levels fromselected devices. For example, selective retrieval may include limitingcommunication from the power monitor 210 to selected optical networkelements 220 based on the capacity or bandwidth of such elements tomanage the load that power monitor 210 places on network 230. In oneexample, power monitor 210 is configured to retrieve actual power levelsfrom cards of 100 gigabytes or greater. In an alternative example,selective retrieval may include communicating with a portion of networkelements at one time period and a remainder at another time period tomanage the load that power monitor 210 places on the network. Othervariations of selectively communicating with the at least one of pluraloptical network elements 220 may be employed.

Power monitor 210 is configured to perform retrieval at a frequency. Thefrequency may vary depending on the number optical network elements 220or other considerations including loads on a particular network, offpeak availability and vendor specifications. For example, the frequencymay be once per month, per week, per day, or other time periods. Thepower monitor 210 is configured to retrieve actual power levels atregular intervals defined by the frequency on a repetitive basis.

Power monitor 210 may include or be connected to a memory 240. As actualpower levels are retrieved, power monitor 210 is configured to store theretrieved actual power levels. These retrieved power levels may bestored along with the date and time of retrieval and an identificationfor the particular optical network element 220. Power monitor 210 may befurther configured to analyze the actual power levels within memory 240to generate trend data for each optical network element. The trend datamay also be stored in memory 240 or another data store. The trend dataincludes actual power levels as a function of time, and may be used todetermine a rate of change in the power level over time. Power monitoris configured to analyze the stored actual power levels and trend datato provide predictive maintenance information as discussed morecompletely below.

Power monitor 210 may further be connected to a data store 250 thatincludes a specified power level for each optical network element withwhich power monitor 210 is in communication. The specified power levelmay include a low water mark and a high water mark, which may simply bereferred to herein as a low mark and a high mark. The low mark and highmark define a specified power level range. The specified power levelrange may be provided within the data store by a vendor to indicate theacceptable operating power level for a particular optical networkelement. An acceptable tolerance may further be provided to broaden ornarrow the operating range for an optical network element. For example,it may be acceptable for the network element to work outside of thespecified power level range by a value less than the low mark andgreater than the high mark. In these instances, acceptable tolerance maybe an absolute value added to the high mark and subtracted from the lowmark in the specified power level range. In other instances, the opticalnetwork element acceptable tolerance may be a value greater than the lowmark and less than the high mark to define a more narrow range than thespecified power level range. This is common where the optical elementwill function within the specified range, but is more prone to producingerrors as the low mark or high mark are approached. To that end, if suchinformation is not available in the data store, power monitor may beconfigured to define an acceptable tolerance or establish an operatingrange that is less than the specified power level range. Defining suchan operating range assists in addressing degrading components prior tofailure as described more completely below.

According to an example, power monitor 210 is configured to compare theactual power level retrieved from the optical network element for anyoptical emitter to the specified power level. Power monitor 210 may beconfigured to generate a signal 260 if the actual power level is outsideof the specified power level by an amount greater than the acceptedtolerance. It will be understood that the accepted tolerance may be zerosuch that an actual power level outside of the specified power levelrange would cause power monitor to generate a signal. The signal mayinclude an alert communicated to an output device 270, such as amonitor, printer, speaker or the like, identifying the particularoptical network device and/or optical emitter that is operating outsideof its normal operating range. The alert may contain a notice to repairor replace the optical network element. In other examples, signal mayinclude an update to the frequency at which actual power level for theoptical network element 220 is retrieved. For example, if power monitor210 checks all optical network elements 220 at a first frequency, anindication that at least one of those optical network elements isoperating outside of the specified power level range, may be used tocause power monitor to retrieve a power level for the particular opticalnetwork element on a second frequency that is different than firstfrequency. For example, second frequency may be greater than the firstto increase the number of actual power level data points and determineif the optical network element 220 is about to fail. The secondfrequency may be implemented for a limited time. For example, if theactual power level returns to a normal operating level for a period oftime, power monitor 210 may determine that the out of range level was ananomaly and return monitoring to the first frequency.

With reference to FIG. 2a , one example methodology implemented throughpower monitor 210 is depicted. Power monitor 210 is configured toretrieve an actual power level of at least one optical network element220 at a first step 211. At a second step 212, power monitor 210compares the retrieved actual power level to a specified power levelhaving high and low water mark values. In the example, if the retrievedvalue is within the high and low water mark values, power monitor 210may further analyze the actual power level to determine if it is nearthe high and low marks. For example, if actual power level is within 10%of either of the high or low mark, power monitor 210 flags the opticalnetwork element as possibly degrading performing a storage step 215 tosave the retrieved value in memory 240, and increasing the retrievalfrequency at a step 216. If the retrieved value is not near the high orlow marks, the power monitor performs a storage step 215, and restartsthe process.

If at step 212, the actual power level retrieved is outside the high andlow mark, at step 214, power monitor determines whether the retrievedvalue is within an acceptable tolerance. If it is not within anacceptable tolerance, the optical network element is judged to be in adegraded or faulty state. Power monitor performs a storage step 215 tosave the retrieved actual power level and generates a signal at 218communicating to an input/output device 270 that repair or replacementof the faulty optical network element 220 is required.

If at step 214, the actual power level is within an acceptabletolerance, a storage step 215 is performed to save the actual powerlevel in memory 240, and power monitor 210 increases the frequency ofretrieval for the affected optical network element at 216.

With continued reference to FIG. 2A, if the retrieved value is outsideof the high and low water mark at step 214 but still within an acceptedtolerance, in addition to storing retrieved value at step 215, system200 may also generate a warning at 219. The warning 219 may be displayedon a suitable input/output device 270 including but not limited to thegraphical user interface described below. Warning 219 may be simplyinformational in nature or warning 219 may include a prompt for input.For example, warning 219 may indicate information including that thenetwork element is outside of the specified range yet within tolerance;the identity of the network element, the location of the networkelement, and/or an indication that the network element will be monitoredmore frequently. Alternatively or in addition to the informationalwarning, an active warning may prompt the user with the option ofdeclining increased monitoring, accepting increased monitoring accordingto the default schedule, or setting a custom monitoring schedule for theselected network element.

With reference to FIG. 2B, an example of an input/output device 270 isdepicted. In the example, input/output device 270 is a graphical userinterface displaying optical network element vendor information 275 foroptical network elements 220 within a selected network 230 for whichpower monitor 210 performs power level retrieval. In the example, powermonitor 210 obtains vendor information 275 from a data store asdiscussed previously. Vendor information 275 may include and identifier276, a reference code 277, such as a common language equipmentidentification code or CLEI code, and a specified power level, generallyindicated by the number 280. Specified power level 280 may include ahigh water mark 281 and a low water mark 282 defining the specifiedpower level range 283. As shown in the example, multiple specified powerlevel ranges may be provided, for example, a client side range and anetwork side range. Likewise, specified power level 283 may definemultiple high and low marks 281,282. In the example, an optical powerreceived (OPR) high and low mark and an optical power transmitted (OPT)high and low mark are provided. The OPR range is broader than the OPTrange. Testing may consider either range (OPR, OPT).

In one example, operation outside of a range may cause power monitor 210to increase the frequency of monitoring to determine if such operationis an indication of degrading performance. Alternatively, operationoutside of a range may be flagged by power monitor 210 in memory suchthat if subsequent retrievals indicate that optical network element 220continues to operate outside of range, the retrieval frequency isincreased. As discussed previously, an acceptable tolerance, generallyindicated at 285, may be used to further evaluate whether opticalnetwork element 220 is operating at an acceptable power level orrequires repair or replacement. The acceptable tolerance 285 may bedefined within vendor information 275, a user definable amount, or atunable amount determined by trend analysis performed by power monitor210. In the example, input/output device 270 displays a user selectabletolerance expressed as multiple percentages (10% and 30%), where theuser in the example has selected a 10% tolerance. It will be understoodthat this is one example and other user inputs including numericalentry, low to high scales, and the like may be used to set a tolerance.The acceptable tolerance may be used to define an operating range 284within specified range 283 by considering a reduction in the range basedon the tolerance level. In the example, acceptable tolerance 285 may beused to reduce the high mark and increase the low mark by a value, suchas the percentages shown. Alternatively, the percentages may be used toincrease the operating range outside of the specified power level range.Using the percentages shown, one operating range within the specifiedpower level range may be 70% of the specified power level range i.e. 30%tolerance reduction. Another example would be 90% of the specified powerlevel range i.e. 10% tolerance reduction. The tolerance reduction may beachieved by reducing high and low water marks by an equal percentage(15%/15% or 5%/5%) in the examples provided or an unequal apportionmentmay be applied. In the alternative example, the specified range could beincreased by the tolerance percentage, such as, 130% of the specifiedrange (30% tolerance) or 110% (10% tolerance). In such situations, powermonitor 210 may evaluate whether the actual power level is within theoperating range 284 i.e. the specified power level range plus or minusthe applicable acceptable tolerance to combine steps 211 and 212 in FIG.2A.

With reference to FIG. 2B, a schedule, generally indicated by the number290 is depicted on an input/output device 270 indicating at least afirst frequency 291 at which power monitor 210 performs a retrieval ofthe actual power level for at least one optical network element 220. Asdescribed above, first frequency 291 may be a preset value, a userdetermined value or a variable value that accounts for load and modifiesthe schedule 290 to perform retrieval during off peak times or istunable by power monitor 210 based on trend data. Schedule 290 mayfurther include a second frequency 292, which like first frequency 291,may be a preset value, a user determined value or a variable value thataccounts for network loads or is tuned by power monitor 210 based ontrend data.

Power monitor 210 may display trend data T on input/output device 270.In the example shown, trend data T may include a representation of theoperating range 284 overlaid thereon. In the example trend data T isprovided along with a signal 295 to repair/replace a particular opticalnetwork element 220. In the example, signal 295 provides the identifier276 for the optical network element, an alert 296 indicatingrepair/replacement is needed along with trend data T.

With reference to FIG. 2C, consideration of the connection betweennetwork elements is considered. It will be understood that multipleoptical network elements may be connected by communication lines, suchas cables or fibers. For simplicity, the example in FIG. 2C depicts afirst network element NE1 and a second network element NE2 opticallyconnected by a fiber F. Each network element has an optical componentthat transmits and receives signals across fiber as indicated by arrows.When measuring OPT and OPR for the network elements, the OPT value is agood indicator of the transmitting performance for the network elementfrom which it is received. OPR, however is dependent upon the signalcoming from another network element and the connection through which thesignal travels. Therefore, in the example shown, OPT and OPR values areretrieved from network element 1. Both values may be evaluated asdescribed above in connection with FIG. 2A. In the flow diagram of FIG.2C, OPT and OPR values are measured to determine if they are within thespecified range. In the example, the measurement is for a first networkelement NE1. If the OPT is out of range, this indicates that atransmitting optical element on first network element NE1 needs repairor replacement. System 200 generates a repair ticket for thecorresponding transmit port on first network element NE1 and stores themeasured value for OPT in memory 240.

If the OPR value for first network element NE1 is out of range, thisdoes not immediately indicate an issue on first network element NE1since the reception of a signal is also dependent on the connectingfiber and the transmitting port on second network element NE2.Therefore, if OPR is out of range, system 200 may flag a possibleproblem with first network element receive port or a dirty or cut fiber.System 200 may also generate a warning ticket to this effect. To attemptto isolate the problem, system 200 may also initiate a paired NE2OPT/OPR analysis. Subsequent to any of the OPT/OPR measurements, system200 stores the respective values in memory 240, as shown.

It will be understood that power monitor 210 may be implemented in anetwork device. FIG. 3. illustrates a functional block diagram depictingone example of a network device, generally indicated at 300. Networkdevice 300 may comprise a processor 302 and a memory 304 coupled toprocessor 302. Memory 304 may contain executable instructions that, whenexecuted by processor 302, cause processor 302 to effectuate operationsassociated with translating parallel protocols between end points infamilies as described above. As evident from the description herein,network device 300 is not to be construed as software per se.

In addition to processor 302 and memory 304, network device 300 mayinclude an input/output system 306. Processor 302, memory 304, andinput/output system 306 may be coupled together to allow communicationsbetween them. Each portion of network device 300 may comprise circuitryfor performing functions associated with each respective portion. Thus,each portion may comprise hardware, or a combination of hardware andsoftware. Accordingly, each portion of network device 300 is not to beconstrued as software per se. Input/output system 306 may be capable ofreceiving or providing information from or to a communications device orother network entities configured for telecommunications. For exampleinput/output system 306 may include a wireless communications (e.g.,3G/4G/GPS) card. Input/output system 306 may be capable of receiving orsending video information, audio information, control information, imageinformation, data, or any combination thereof. Input/output system 306may be capable of transferring information with network device 300. Invarious configurations, input/output system 306 may receive or provideinformation via any appropriate means, such as, for example, opticalmeans (e.g., infrared), electromagnetic means (e.g., RF, Wi-Fi,Bluetooth®, ZigBee®), acoustic means (e.g., speaker, microphone,ultrasonic receiver, ultrasonic transmitter), electrical means, or acombination thereof. In an example configuration, input/output system306 may comprise a Wi-Fi finder, a two-way GPS chipset or equivalent, orthe like, or a combination thereof. Bluetooth, infrared, NFC, and Zigbeeare generally considered short range (e.g., few centimeters to 20meters). WiFi is considered medium range (e.g., approximately 100meters).

Input/output system 306 of network device 300 also may contain acommunication connection 308 that allows network device 300 tocommunicate with other devices, network entities, or the like.Communication connection 308 may comprise communication media.Communication media typically embody computer-readable instructions,data structures, program modules or other data in a modulated datasignal such as a carrier wave or other transport mechanism and includesany information delivery media. By way of example, and not limitation,communication media may include wired media such as a wired network ordirect-wired connection, or wireless media such as acoustic, RF,infrared, or other wireless media. The term computer-readable media asused herein includes both storage media and communication media.Input/output system 306 also may include an input device 310 such askeyboard, mouse, pen, voice input device, or touch input device.Input/output system 306 may also include an output device 312, such as adisplay, speakers, or a printer.

Processor 302 may be capable of performing functions associated withtelecommunications, such as functions for processing broadcast messages,as described herein. For example, processor 302 may be capable of, inconjunction with any other portion of network device 300, determining atype of broadcast message and acting according to the broadcast messagetype or content, as described herein.

Memory 304 of network device 300 may comprise a storage medium having aconcrete, tangible, physical structure. As is known, a signal does nothave a concrete, tangible, physical structure. Memory 304, as well asany computer-readable storage medium described herein, is not to beconstrued as a signal. Memory 304, as well as any computer-readablestorage medium described herein, is not to be construed as a transientsignal. Memory 304, as well as any computer-readable storage mediumdescribed herein, is not to be construed as a propagating signal. Memory304, as well as any computer-readable storage medium described herein,is to be construed as an article of manufacture.

Memory 304 may store any information utilized in conjunction withtelecommunications. Depending upon the exact configuration or type ofprocessor, memory 304 may include a volatile storage 314 (such as sometypes of RAM), a nonvolatile storage 316 (such as ROM, flash memory), ora combination thereof. Memory 304 may include additional storage (e.g.,a removable storage 318 or a non-removable storage 320) including, forexample, tape, flash memory, smart cards, CD-ROM, DVD, or other opticalstorage, magnetic cassettes, magnetic tape, magnetic disk storage orother magnetic storage devices, USB-compatible memory, or any othermedium that can be used to store information and that can be accessed bynetwork device 300. Memory 304 may comprise executable instructionsthat, when executed by processor 302, cause processor 302 to effectuateoperations to map signal strengths in an area of interest.

BAFX 250 may reside within any network to facilitate communicationbetween edge routers from disparate network families and services. Thefollowing are example networks on which BAFX 250 may reside. Forpurposes of centrality, BAFX 250 may reside within a core network shownin the various examples below. However, it will be understood that BAFX250 may reside on any network where communication between families withdifferent protocols is desired including but not limited totelecommunications networks, internet, and other networks described morecompletely below.

FIG. 4 illustrates a functional block diagram depicting one example ofan LTE-EPS network architecture 400 that may be at least partiallyimplemented as an SDN. Network architecture 400 disclosed herein isreferred to as a modified LTE-EPS architecture 400 to distinguish itfrom a traditional LTE-EPS architecture.

An example modified LTE-EPS architecture 400 is based at least in parton standards developed by the 3rd Generation Partnership Project (3GPP),with information available at www.3gpp.org. LTE-EPS network architecture400 may include an access network 402, a core network 404, e.g., an EPCor Common BackBone (CBB) and one or more external networks 406,sometimes referred to as PDN or peer entities. Different externalnetworks 406 can be distinguished from each other by a respectivenetwork identifier, e.g., a label according to DNS naming conventionsdescribing an access point to the PDN. Such labels can be referred to asAccess Point Names (APN). External networks 406 can include one or moretrusted and non-trusted external networks such as an internet protocol(IP) network 408, an IP multimedia subsystem (IMS) network 410, andother networks 412, such as a service network, a corporate network, orthe like. In an aspect, access network 402, core network 404, orexternal network 405 may include or communicate with network 100.

Access network 402 can include an LTE network architecture sometimesreferred to as Evolved Universal mobile Telecommunication systemTerrestrial Radio Access (E UTRA) and evolved UMTS Terrestrial RadioAccess Network (E-UTRAN). Broadly, access network 402 can include one ormore communication devices, commonly referred to as UE 414, and one ormore wireless access nodes, or base stations 416 a, 416 b. Duringnetwork operations, at least one base station 416 communicates directlywith UE 414. Base station 416 can be an evolved Node B (e-NodeB), withwhich UE 414 communicates over the air and wirelessly. UEs 414 caninclude, without limitation, wireless devices, e.g., satellitecommunication systems, portable digital assistants (PDAs), laptopcomputers, tablet devices and other mobile devices (e.g., cellulartelephones, smart appliances, and so on). UEs 414 can connect to eNBs416 when UE 414 is within range according to a corresponding wirelesscommunication technology.

UE 414 generally runs one or more applications that engage in a transferof packets between UE 414 and one or more external networks 406. Suchpacket transfers can include one of downlink packet transfers fromexternal network 406 to UE 414, uplink packet transfers from UE 414 toexternal network 406 or combinations of uplink and downlink packettransfers. Applications can include, without limitation, web browsing,VoIP, streaming media and the like. Each application can pose differentQuality of Service (QoS) requirements on a respective packet transfer.Different packet transfers can be served by different bearers withincore network 404, e.g., according to parameters, such as the QoS.

Core network 404 uses a concept of bearers, e.g., EPS bearers, to routepackets, e.g., IP traffic, between a particular gateway in core network404 and UE 414. A bearer refers generally to an IP packet flow with adefined QoS between the particular gateway and UE 414. Access network402, e.g., E UTRAN, and core network 404 together set up and releasebearers as required by the various applications. Bearers can beclassified in at least two different categories: (i) minimum guaranteedbit rate bearers, e.g., for applications, such as VoIP; and (ii)non-guaranteed bit rate bearers that do not require guarantee bit rate,e.g., for applications, such as web browsing.

In one embodiment, the core network 404 includes various networkentities, such as MME 418, SGW 420, Home Subscriber Server (HSS) 422,Policy and Charging Rules Function (PCRF) 424 and PDN gateway (PGW) 426.According to the example, PGW 426 is an exchange 200 according to theexample described above. PGW 426 may include a BAFX 250 as discussedabove. In one embodiment, MME 418 comprises a control node performing acontrol signaling between various equipment and devices in accessnetwork 402 and core network 404. The protocols running between UE 414and core network 404 are generally known as Non-Access Stratum (NAS)protocols.

For illustration purposes only, the terms MME 418, SGW 420, HSS 422 andPGW 426, and so on, can be server devices, but may be referred to in thesubject disclosure without the word “server.” It is also understood thatany form of such servers can operate in a device, system, component, orother form of centralized or distributed hardware and software. It isfurther noted that these terms and other terms such as bearer pathsand/or interfaces are terms that can include features, methodologies,and/or fields that may be described in whole or in part by standardsbodies such as the 3GPP. It is further noted that some or allembodiments of the subject disclosure may in whole or in part modify,supplement, or otherwise supersede final or proposed standards publishedand promulgated by 3GPP.

According to traditional implementations of LTE-EPS architectures, SGW420 routes and forwards all user data packets. SGW 420 also acts as amobility anchor for user plane operation during handovers between basestations, e.g., during a handover from first eNB 416 a to second eNB 416b as may be the result of UE 414 moving from one area of coverage, e.g.,cell, to another. SGW 420 can also terminate a downlink data path, e.g.,from external network 406 to UE 414 in an idle state, and trigger apaging operation when downlink data arrives for UE 414. SGW 420 can alsobe configured to manage and store a context for UE 414, e.g., includingone or more of parameters of the IP bearer service and network internalrouting information. In addition, SGW 420 can perform administrativefunctions, e.g., in a visited network, such as collecting informationfor charging (e.g., the volume of data sent to or received from theuser), and/or replicate user traffic, e.g., to support a lawfulinterception. SGW 420 also serves as the mobility anchor forinterworking with other 3GPP technologies such as universal mobiletelecommunication system (UMTS).

At any given time, UE 414 is generally in one of three different states:detached, idle, or active. The detached state is typically a transitorystate in which UE 414 is powered on but is engaged in a process ofsearching and registering with network 402. In the active state, UE 414is registered with access network 402 and has established a wirelessconnection, e.g., radio resource control (RRC) connection, with eNB 416.Whether UE 414 is in an active state can depend on the state of a packetdata session, and whether there is an active packet data session. In theidle state, UE 414 is generally in a power conservation state in whichUE 414 typically does not communicate packets. When UE 414 is idle, SGW420 can terminate a downlink data path, e.g., from one peer entity 406,and triggers paging of UE 414 when data arrives for UE 414. If UE 414responds to the page, SGW 420 can forward the IP packet to eNB 416 a.

HSS 422 can manage subscription-related information for a user of UE414. For example, tHSS 422 can store information such as authorizationof the user, security requirements for the user, quality of service(QoS) requirements for the user, etc. HSS 422 can also hold informationabout external networks 406 to which the user can connect, e.g., in theform of an APN of external networks 406. For example, MME 418 cancommunicate with HSS 422 to determine if UE 414 is authorized toestablish a call, e.g., a voice over IP (VoIP) call before the call isestablished.

PCRF 424 can perform QoS management functions and policy control. PCRF424 is responsible for policy control decision-making, as well as forcontrolling the flow-based charging functionalities in a policy controlenforcement function (PCEF), which resides in PGW 426, PCRF 424 providesthe QoS authorization, e.g., QoS class identifier and bit rates thatdecide how a certain data flow will be treated in the PCEF and ensuresthat this is in accordance with the user's subscription profile.

PGW 426 can provide connectivity between the UE 414 and one or more ofthe external networks 406. In illustrative network architecture 400, PGW426 can be responsible for IP address allocation for UE 414, as well asone or more of QoS enforcement and flow-based charging, e.g., accordingto rules from the PCRF 424. PGW 426 is also typically responsible forfiltering downlink user IP packets into the different QoS-based bearers.In at least some embodiments, such filtering can be performed based ontraffic flow templates. PGW 426 can also perform QoS enforcement, e.g.,for guaranteed bit rate bearers. PGW 426 also serves as a mobilityanchor for interworking with non-3GPP technologies such as CDMA2000.

Within access network 402 and core network 404 there may be variousbearer paths/interfaces, e.g., represented by solid lines 428 and 430.Some of the bearer paths can be referred to by a specific label. Forexample, solid line 428 can be considered an S1-U bearer and solid line432 can be considered an S5/S8 bearer according to LTE-EPS architecturestandards. Without limitation, reference to various interfaces, such asS1, X2, S5, S8, S11 refer to EPS interfaces. In some instances, suchinterface designations are combined with a suffix, e.g., a “U” or a “C”to signify whether the interface relates to a “User plane” or a “Controlplane.” In addition, the core network 404 can include various signalingbearer paths/interfaces, e.g., control plane paths/interfacesrepresented by dashed lines 430, 434, 436, and 438. Some of thesignaling bearer paths may be referred to by a specific label. Forexample, dashed line 430 can be considered as an S1-MME signalingbearer, dashed line 434 can be considered as an S11 signaling bearer anddashed line 436 can be considered as an S6a signaling bearer, e.g.,according to LTE-EPS architecture standards. The above bearer paths andsignaling bearer paths are only illustrated as examples and it should benoted that additional bearer paths and signaling bearer paths may existthat are not illustrated.

Also shown is a novel user plane path/interface, referred to as theS1-U+ interface 466. In the illustrative example, the S1-U+ user planeinterface extends between the eNB 416 a and PGW 426. Notably, S1-U+path/interface does not include SGW 420, a node that is otherwiseinstrumental in configuring and/or managing packet forwarding betweeneNB 416 a and one or more external networks 406 by way of PGW 426. Asdisclosed herein, the S1-U+ path/interface facilitates autonomouslearning of peer transport layer addresses by one or more of the networknodes to facilitate a self-configuring of the packet forwarding path. Inparticular, such self-configuring can be accomplished during handoversin most scenarios so as to reduce any extra signaling load on the S/PGWs420, 426 due to excessive handover events.

In some embodiments, PGW 426 is coupled to storage device 440, shown inphantom. Storage device 440 can be integral to one of the network nodes,such as PGW 426, for example, in the form of internal memory and/or diskdrive. It is understood that storage device 440 can include registerssuitable for storing address values. Alternatively or in addition,storage device 440 can be separate from PGW 426, for example, as anexternal hard drive, a flash drive, and/or network storage.

Storage device 440 selectively stores one or more values relevant to theforwarding of packet data. For example, storage device 440 can storeidentities and/or addresses of network entities, such as any of networknodes 418, 420, 422, 424, and 426, eNBs 416 and/or UE 414. In theillustrative example, storage device 440 includes a first storagelocation 442 and a second storage location 444. First storage location442 can be dedicated to storing a Currently Used Downlink address value442. Likewise, second storage location 444 can be dedicated to storing aDefault Downlink Forwarding address value 444. PGW 426 can read and/orwrite values into either of storage locations 442, 444, for example,managing Currently Used Downlink Forwarding address value 442 andDefault Downlink Forwarding address value 444 as disclosed herein.

In some embodiments, the Default Downlink Forwarding address for eachEPS bearer is the SGW S5-U address for each EPS Bearer. The CurrentlyUsed Downlink Forwarding address” for each EPS bearer in PGW 426 can beset every time when PGW 426 receives an uplink packet, e.g., a GTP-Uuplink packet, with a new source address for a corresponding EPS bearer.When UE 414 is in an idle state, the “Current Used Downlink Forwardingaddress” field for each EPS bearer of UE 414 can be set to a “null” orother suitable value.

In some embodiments, the Default Downlink Forwarding address is onlyupdated when PGW 426 receives a new SGW S5-U address in a predeterminedmessage or messages. For example, the Default Downlink Forwardingaddress is only updated when PGW 426 receives one of a Create SessionRequest, Modify Bearer Request and Create Bearer Response messages fromSGW 420.

As values 442, 444 can be maintained and otherwise manipulated on a perbearer basis, it is understood that the storage locations can take theform of tables, spreadsheets, lists, and/or other data structuresgenerally well understood and suitable for maintaining and/or otherwisemanipulate forwarding addresses on a per bearer basis.

It should be noted that access network 402 and core network 404 areillustrated in a simplified block diagram in FIG. 4. In other words,either or both of access network 402 and the core network 404 caninclude additional network elements that are not shown, such as variousrouters, switches and controllers. In addition, although FIG. 4illustrates only a single one of each of the various network elements,it should be noted that access network 402 and core network 404 caninclude any number of the various network elements. For example, corenetwork 404 can include a pool (i.e., more than one) of MMEs 418, SGWs420 or PGWs 426.

In the illustrative example, data traversing a network path between UE414, eNB 416 a, SGW 420, PGW 426 and external network 406 may beconsidered to constitute data transferred according to an end-to-end IPservice. However, for the present disclosure, to properly performestablishment management in LTE-EPS network architecture 400, the corenetwork, data bearer portion of the end-to-end IP service is analyzed.

An establishment may be defined herein as a connection set up requestbetween any two elements within LTE-EPS network architecture 400. Theconnection set up request may be for user data or for signaling. Afailed establishment may be defined as a connection set up request thatwas unsuccessful. A successful establishment may be defined as aconnection set up request that was successful.

In one embodiment, a data bearer portion comprises a first portion(e.g., a data radio bearer 446) between UE 414 and eNB 416 a, a secondportion (e.g., an S1 data bearer 428) between eNB 416 a and SGW 420, anda third portion (e.g., an S5/S8 bearer 432) between SGW 420 and PGW 426.Various signaling bearer portions are also illustrated in FIG. 4. Forexample, a first signaling portion (e.g., a signaling radio bearer 448)between UE 414 and eNB 416 a, and a second signaling portion (e.g., S1signaling bearer 430) between eNB 416 a and MME 418.

In at least some embodiments, the data bearer can include tunneling,e.g., IP tunneling, by which data packets can be forwarded in anencapsulated manner, between tunnel endpoints. Tunnels, or tunnelconnections can be identified in one or more nodes of network 100, e.g.,by one or more of tunnel endpoint identifiers, an IP address and a userdatagram protocol port number. Within a particular tunnel connection,payloads, e.g., packet data, which may or may not include protocolrelated information, are forwarded between tunnel endpoints.

An example of first tunnel solution 450 includes a first tunnel 452 abetween two tunnel endpoints 454 a and 456 a, and a second tunnel 452 bbetween two tunnel endpoints 454 b and 456 b. In the illustrativeexample, first tunnel 452 a is established between eNB 416 a and SGW420. Accordingly, first tunnel 452 a includes a first tunnel endpoint454 a corresponding to an S1-U address of eNB 416 a (referred to hereinas the eNB S1-U address), and second tunnel endpoint 456 a correspondingto an S1-U address of SGW 420 (referred to herein as the SGW S1-Uaddress). Likewise, second tunnel 452 b includes first tunnel endpoint454 b corresponding to an S5-U address of SGW 420 (referred to herein asthe SGW S5-U address), and second tunnel endpoint 456 b corresponding toan S5-U address of PGW 426 (referred to herein as the PGW S5-U address).

In at least some embodiments, first tunnel solution 450 is referred toas a two tunnel solution, e.g., according to the GPRS Tunneling ProtocolUser Plane (GTPv1-U based), as described in 3GPP specification TS29.281, incorporated herein in its entirety. It is understood that oneor more tunnels are permitted between each set of tunnel end points. Forexample, each subscriber can have one or more tunnels, e.g., one foreach PDP context that they have active, as well as possibly havingseparate tunnels for specific connections with different quality ofservice requirements, and so on.

An example of second tunnel solution 458 includes a single or directtunnel 460 between tunnel endpoints 462 and 464. In the illustrativeexample, direct tunnel 460 is established between eNB 416 a and PGW 426,without subjecting packet transfers to processing related to SGW 420.Accordingly, direct tunnel 460 includes first tunnel endpoint 462corresponding to the eNB S1-U address, and second tunnel endpoint 464corresponding to the PGW S5-U address. Packet data received at eitherend can be encapsulated into a payload and directed to the correspondingaddress of the other end of the tunnel. Such direct tunneling avoidsprocessing, e.g., by SGW 420 that would otherwise relay packets betweenthe same two endpoints, e.g., according to a protocol, such as the GTP-Uprotocol.

In some scenarios, direct tunneling solution 458 can forward user planedata packets between eNB 416 a and PGW 426, by way of SGW 420. That is,SGW 420 can serve a relay function, by relaying packets between twotunnel endpoints 416 a, 426. In other scenarios, direct tunnelingsolution 458 can forward user data packets between eNB 416 a and PGW426, by way of the S1 U+ interface, thereby bypassing SGW 420.

Generally, UE 414 can have one or more bearers at any one time. Thenumber and types of bearers can depend on applications, defaultrequirements, and so on. It is understood that the techniques disclosedherein, including the configuration, management and use of varioustunnel solutions 450, 458, can be applied to the bearers on anindividual bases. That is, if user data packets of one bearer, say abearer associated with a VoIP service of UE 414, then the forwarding ofall packets of that bearer are handled in a similar manner. Continuingwith this example, the same UE 414 can have another bearer associatedwith it through the same eNB 416 a. This other bearer, for example, canbe associated with a relatively low rate data session forwarding userdata packets through core network 404 simultaneously with the firstbearer. Likewise, the user data packets of the other bearer are alsohandled in a similar manner, without necessarily following a forwardingpath or solution of the first bearer. Thus, one of the bearers may beforwarded through direct tunnel 458; whereas, another one of the bearersmay be forwarded through a two-tunnel solution 450.

FIG. 5 depicts an exemplary diagrammatic representation of a machine inthe form of a computer system 500 within which a set of instructions,when executed, may cause the machine to perform any one or more of themethods described above. One or more instances of the machine canoperate, for example, as a processor 302, UE 414, eNB 416, MME 418, SGW420, HSS 422, PCRF 424, PGW 426 and other devices of FIGS. 1, 2, and 4.In some embodiments, the machine may be connected (e.g., using a network502) to other machines. In a networked deployment, the machine mayoperate in the capacity of a server or a client user machine in aserver-client user network environment, or as a peer machine in apeer-to-peer (or distributed) network environment. As depicted in suchinstances, computer system 500 may operate as an exchange 200.

The machine may comprise a server computer, a client user computer, apersonal computer (PC), a tablet, a smart phone, a laptop computer, adesktop computer, a control system, a network router, switch or bridge,or any machine capable of executing a set of instructions (sequential orotherwise) that specify actions to be taken by that machine. It will beunderstood that a communication device of the subject disclosureincludes broadly any electronic device that provides voice, video ordata communication. Further, while a single machine is illustrated, theterm “machine” shall also be taken to include any collection of machinesthat individually or jointly execute a set (or multiple sets) ofinstructions to perform any one or more of the methods discussed herein.

Computer system 500 may include a processor (or controller) 504 (e.g., acentral processing unit (CPU)), a graphics processing unit (GPU, orboth), a main memory 506 and a static memory 508, which communicate witheach other via a bus 510. The computer system 500 may further include adisplay unit 512 (e.g., a liquid crystal display (LCD), a flat panel, ora solid state display). Computer system 500 may include an input device514 (e.g., a keyboard), a cursor control device 516 (e.g., a mouse), adisk drive unit 518, a signal generation device 520 (e.g., a speaker orremote control) and a network interface device 522. In distributedenvironments, the embodiments described in the subject disclosure can beadapted to utilize multiple display units 512 controlled by two or morecomputer systems 500. In this configuration, presentations described bythe subject disclosure may in part be shown in a first of display units512, while the remaining portion is presented in a second of displayunits 512.

The disk drive unit 518 may include a tangible computer-readable storagemedium 524 on which is stored one or more sets of instructions (e.g.,software 526) embodying any one or more of the methods or functionsdescribed herein, including those methods illustrated above.Instructions 526 may also reside, completely or at least partially,within main memory 506, static memory 508, or within processor 504during execution thereof by the computer system 500. Main memory 506 andprocessor 504 also may constitute tangible computer-readable storagemedia.

As shown in FIG. 6, telecommunication system 600 may include wirelesstransmit/receive units (WTRUs) 602, a RAN 604, a core network 606, apublic switched telephone network (PSTN) 608, the Internet 610, or othernetworks 612, though it will be appreciated that the disclosed examplescontemplate any number of WTRUs, base stations, networks, or networkelements. As previously discussed, core network 606 may house exchange200 that includes a BAFX 250 as best shown in FIGS. 2-2 b incorporatedby reference.

Each WTRU 602 may be any type of device configured to operate orcommunicate in a wireless environment. For example, a WTRU may comprisedrone 102, a mobile device, network device 300, or the like, or anycombination thereof. By way of example, WTRUs 602 may be configured totransmit or receive wireless signals and may include a UE, a mobilestation, a mobile device, a fixed or mobile subscriber unit, a pager, acellular telephone, a PDA, a smartphone, a laptop, a netbook, a personalcomputer, a wireless sensor, consumer electronics, or the like. WTRUs602 may be configured to transmit or receive wireless signals over anair interface 614.

Telecommunication system 600 may also include one or more base stations616. Each of base stations 616 may be any type of device configured towirelessly interface with at least one of the WTRUs 602 to facilitateaccess to one or more communication networks, such as core network 606,PTSN 608, Internet 610, or other networks 612. By way of example, basestations 616 may be a base transceiver station (BTS), a Node-B, an eNodeB, a Home Node B, a Home eNode B, a site controller, an access point(AP), a wireless router, or the like. While base stations 616 are eachdepicted as a single element, it will be appreciated that base stations616 may include any number of interconnected base stations or networkelements.

RAN 604 may include one or more base stations 616, along with othernetwork elements (not shown), such as a base station controller (BSC), aradio network controller (RNC), or relay nodes. One or more basestations 616 may be configured to transmit or receive wireless signalswithin a particular geographic region, which may be referred to as acell (not shown). The cell may further be divided into cell sectors. Forexample, the cell associated with base station 616 may be divided intothree sectors such that base station 616 may include three transceivers:one for each sector of the cell. In another example, base station 616may employ multiple-input multiple-output (MIMO) technology and,therefore, may utilize multiple transceivers for each sector of thecell.

Base stations 616 may communicate with one or more of WTRUs 602 over airinterface 614, which may be any suitable wireless communication link(e.g., RF, microwave, infrared (IR), ultraviolet (UV), or visiblelight). Air interface 614 may be established using any suitable radioaccess technology (RAT).

More specifically, as noted above, telecommunication system 600 may be amultiple access system and may employ one or more channel accessschemes, such as CDMA, TDMA, FDMA, OFDMA, SC-FDMA, or the like. Forexample, base station 616 in RAN 604 and WTRUs 602 connected to RAN 604may implement a radio technology such as Universal MobileTelecommunications System (UMTS) Terrestrial Radio Access (UTRA) thatmay establish air interface 614 using wideband CDMA (WCDMA). WCDMA mayinclude communication protocols, such as High-Speed Packet Access (HSPA)or Evolved HSPA (HSPA+). HSPA may include High-Speed Downlink PacketAccess (HSDPA) or High-Speed Uplink Packet Access (HSUPA).

As another example base station 616 and WTRUs 602 that are connected toRAN 604 may implement a radio technology such as Evolved UMTSTerrestrial Radio Access (E-UTRA), which may establish air interface 614using LTE or LTE-Advanced (LTE-A).

Optionally base station 616 and WTRUs 602 connected to RAN 604 mayimplement radio technologies such as IEEE 602.16 (i.e., WorldwideInteroperability for Microwave Access (WiMAX)), CDMA2000, CDMA2000 1×,CDMA2000 EV-DO, Interim Standard 2000 (IS-2000), Interim Standard 95(IS-95), Interim Standard 856 (IS-856), GSM, Enhanced Data rates for GSMEvolution (EDGE), GSM EDGE (GERAN), or the like.

Base station 616 may be a wireless router, Home Node B, Home eNode B, oraccess point, for example, and may utilize any suitable RAT forfacilitating wireless connectivity in a localized area, such as a placeof business, a home, a vehicle, a campus, or the like. For example, basestation 616 and associated WTRUs 602 may implement a radio technologysuch as IEEE 602.11 to establish a wireless local area network (WLAN).As another example, base station 616 and associated WTRUs 602 mayimplement a radio technology such as IEEE 602.15 to establish a wirelesspersonal area network (WPAN). In yet another example, base station 616and associated WTRUs 602 may utilize a cellular-based RAT (e.g., WCDMA,CDMA2000, GSM, LTE, LTE-A, etc.) to establish a picocell or femtocell.As shown in FIG. 6, base station 616 may have a direct connection toInternet 610. Thus, base station 616 may not be required to accessInternet 610 via core network 606.

RAN 604 may be in communication with core network 606, which may be anytype of network configured to provide voice, data, applications, and/orvoice over internet protocol (VoIP) services to one or more WTRUs 602.For example, core network 606 may provide call control, billingservices, mobile location-based services, pre-paid calling, Internetconnectivity, video distribution or high-level security functions, suchas user authentication. Although not shown in FIG. 6, it will beappreciated that RAN 604 or core network 606 may be in direct orindirect communication with other RANs that employ the same RAT as RAN604 or a different RAT. For example, in addition to being connected toRAN 604, which may be utilizing an E-UTRA radio technology, core network606 may also be in communication with another RAN (not shown) employinga GSM radio technology.

Core network 606 may also serve as a gateway for WTRUs 602 to accessPSTN 608, Internet 610, or other networks 612. PSTN 608 may includecircuit-switched telephone networks that provide plain old telephoneservice (POTS). For LTE core networks, core network 606 may use IMS core614 to provide access to PSTN 608. Internet 610 may include a globalsystem of interconnected computer networks or devices that use commoncommunication protocols, such as the transmission control protocol(TCP), user datagram protocol (UDP), or IP in the TCP/IP internetprotocol suite. Other networks 612 may include wired or wirelesscommunications networks owned or operated by other service providers.For example, other networks 612 may include another core networkconnected to one or more RANs, which may employ the same RAT as RAN 604or a different RAT.

Some or all WTRUs 602 in telecommunication system 600 may includemulti-mode capabilities. That is, WTRUs 602 may include multipletransceivers for communicating with different wireless networks overdifferent wireless links. For example, one or more WTRUs 602 may beconfigured to communicate with base station 616, which may employ acellular-based radio technology, and with base station 616, which mayemploy an IEEE 802 radio technology.

FIG. 7 is an example system 700 including RAN 604 and core network 606.As noted above, RAN 604 may employ an E-UTRA radio technology tocommunicate with WTRUs 602 over air interface 614. RAN 604 may also bein communication with core network 606.

RAN 604 may include any number of eNode-Bs 702 while remainingconsistent with the disclosed technology. One or more eNode-Bs 702 mayinclude one or more transceivers for communicating with the WTRUs 602over air interface 614. Optionally, eNode-Bs 702 may implement MIMOtechnology. Thus, one of eNode-Bs 702, for example, may use multipleantennas to transmit wireless signals to, or receive wireless signalsfrom, one of WTRUs 602.

Each of eNode-Bs 702 may be associated with a particular cell and may beconfigured to handle radio resource management decisions, handoverdecisions, scheduling of users in the uplink or downlink, or the like.As shown in FIG. 7 eNode-Bs 702 may communicate with one another over anX2 interface.

Core network 606 shown in FIG. 7 may include a mobility managementgateway or entity (MME) 704, a serving gateway 706, or a packet datanetwork (PDN) gateway 708. As discussed with reference to FIG. 6, corenetwork 606 may include an exchange 200 with a BAFX. As discussed inmore detail above, exchange 200 may take on the role and eliminate adata plane gateway, such as PDN 708. While each of the foregoingelements are depicted as part of core network 606, it will beappreciated that any one of these elements may be owned or operated byan entity other than the core network operator.

MME 704 may be connected to each of eNode-Bs 702 in RAN 604 via an S1interface and may serve as a control node. For example, MME 704 may beresponsible for authenticating users of WTRUs 602, bearer activation ordeactivation, selecting a particular serving gateway during an initialattach of WTRUs 602, or the like. MME 704 may also provide a controlplane function for switching between RAN 604 and other RANs (not shown)that employ other radio technologies, such as GSM or WCDMA.

Serving gateway 706 may be connected to each of eNode-Bs 702 in RAN 604via the S1 interface. Serving gateway 706 may generally route or forwarduser data packets to or from the WTRUs 602. Serving gateway 706 may alsoperform other functions, such as anchoring user planes duringinter-eNode B handovers, triggering paging when downlink data isavailable for WTRUs 602, managing or storing contexts of WTRUs 602, orthe like.

Serving gateway 706 may also be connected to PDN gateway 708, which mayprovide WTRUs 602 with access to packet-switched networks, such asInternet 610, to facilitate communications between WTRUs 602 andIP-enabled devices.

Core network 606 may facilitate communications with other networks. Forexample, core network 606 may provide WTRUs 602 with access tocircuit-switched networks, such as PSTN 608, such as through IMS core614, to facilitate communications between WTRUs 602 and traditionalland-line communications devices. In addition, core network 606 mayprovide the WTRUs 602 with access to other networks 612, which mayinclude other wired or wireless networks that are owned or operated byother service providers.

FIG. 8 depicts an overall block diagram of an example packet-basedmobile cellular network environment, such as a GPRS network as describedherein. In the example packet-based mobile cellular network environmentshown in FIG. 8, there are a plurality of base station subsystems (BSS)800 (only one is shown), each of which comprises a base stationcontroller (BSC) 802 serving a plurality of BTSs, such as BTSs 804, 806,808. BTSs 804, 806, 808 are the access points where users ofpacket-based mobile devices become connected to the wireless network. Inexample fashion, the packet traffic originating from mobile devices istransported via an over-the-air interface to BTS 808, and from BTS 808to BSC 802. Base station subsystems, such as BSS 800, are a part ofinternal frame relay network 810 that can include a service GPRS supportnodes (SGSN), such as SGSN 812 or SGSN 814. Each SGSN 812, 814 isconnected to an internal packet network 816 through which SGSN 812, 814can route data packets to or from a plurality of gateway GPRS supportnodes (GGSN) 818, 820, 822. As illustrated, SGSN 814 and GGSNs 818, 820,822 are part of internal packet network 816. GGSNs 818, 820, 822 mainlyprovide an interface to external IP networks such as PLMN 824, corporateintranets/internets 826, or Fixed-End System (FES) or the publicInternet 828. As illustrated, subscriber corporate network 826 may beconnected to GGSN 820 via a firewall 830. PLMN 824 may be connected toGGSN 820 via a border gateway router (BGR) 832. According to theexamples described above, GGSNs may include an exchange 200 including aBAFX 250 to facilitate the interface between various networks, corporateintranets/internets, fixed end systems and public internet. A RemoteAuthentication Dial-In User Service (RADIUS) server 834 may be used forcaller authentication when a user calls corporate network 826.

Generally, there may be a several cell sizes in a network, referred toas macro, micro, pico, femto or umbrella cells. The coverage area ofeach cell is different in different environments. Macro cells can beregarded as cells in which the base station antenna is installed in amast or a building above average roof top level. Micro cells are cellswhose antenna height is under average roof top level. Micro cells aretypically used in urban areas. Pico cells are small cells having adiameter of a few dozen meters. Pico cells are used mainly indoors.Femto cells have the same size as pico cells, but a smaller transportcapacity. Femto cells are used indoors, in residential or small businessenvironments. On the other hand, umbrella cells are used to covershadowed regions of smaller cells and fill in gaps in coverage betweenthose cells.

FIG. 9 illustrates an architecture of a typical GPRS network 900 asdescribed herein. The architecture depicted in FIG. 9 may be segmentedinto four groups: users 902, RAN 904, core network 906, and interconnectnetwork 908. Users 902 comprise a plurality of end users, who each mayuse one or more devices 910. Note that device 910 is referred to as amobile subscriber (MS) in the description of network shown in FIG. 9. Inan example, device 910 comprises a communications device (e.g., mobiledevice 102, mobile positioning center 116, network device 300, any ofdetected devices 500, second device 508, access device 604, accessdevice 606, access device 608, access device 610 or the like, or anycombination thereof). Radio access network 904 comprises a plurality ofBSSs such as BSS 912, which includes a BTS 914 and a BSC 916. Corenetwork 906 may include a host of various network elements. Asillustrated in FIG. 9, core network 906 may comprise MSC 918, servicecontrol point (SCP) 920, gateway MSC (GMSC) 922, SGSN 924, home locationregister (HLR) 926, authentication center (AuC) 928, domain name system(DNS) server 930, and GGSN 932. Interconnect network 908 may alsocomprise a host of various networks or other network elements. Asillustrated in FIG. 9, interconnect network 908 comprises a PSTN 934, anFES/Internet 936, a firewall 938, or a corporate network 940.

An MSC can be connected to a large number of BSCs. At MSC 918, forinstance, depending on the type of traffic, the traffic may be separatedin that voice may be sent to PSTN 934 through GMSC 922, or data may besent to SGSN 924, which then sends the data traffic to GGSN 932 forfurther forwarding.

When MSC 918 receives call traffic, for example, from BSC 916, it sendsa query to a database hosted by SCP 920, which processes the request andissues a response to MSC 918 so that it may continue call processing asappropriate.

HLR 926 is a centralized database for users to register to the GPRSnetwork. HLR 926 stores static information about the subscribers such asthe International Mobile Subscriber Identity (IMSI), subscribedservices, or a key for authenticating the subscriber. HLR 926 alsostores dynamic subscriber information such as the current location ofthe MS. Associated with HLR 926 is AuC 928, which is a database thatcontains the algorithms for authenticating subscribers and includes theassociated keys for encryption to safeguard the user input forauthentication.

In the following, depending on context, “mobile subscriber” or “MS”sometimes refers to the end user and sometimes to the actual portabledevice, such as a mobile device, used by an end user of the mobilecellular service. When a mobile subscriber turns on his or her mobiledevice, the mobile device goes through an attach process by which themobile device attaches to an of the GPRS network. In FIG. 9, when MS 910initiates the attach process by turning on the network capabilities ofthe mobile device, an attach request is sent by MS 910 to SGSN 924. TheSGSN 924 queries another SGSN, to which MS 910 was attached before, forthe identity of MS 910. Upon receiving the identity of MS 910 from theother SGSN, SGSN 924 requests more information from MS 910. Thisinformation is used to authenticate MS 910 together with the informationprovided by HLR 926. Once verified, SGSN 924 sends a location update toHLR 926 indicating the change of location to a new SGSN, in this caseSGSN 924. HLR 926 notifies the old SGSN, to which MS 910 was attachedbefore, to cancel the location process for MS 910. HLR 926 then notifiesSGSN 924 that the location update has been performed. At this time, SGSN924 sends an Attach Accept message to MS 910, which in turn sends anAttach Complete message to SGSN 924.

Next, MS 910 establishes a user session with the destination network,corporate network 940, by going through a Packet Data Protocol (PDP)activation process. Briefly, in the process, MS 910 requests access tothe Access Point Name (APN), for example, UPS.com, and SGSN 924 receivesthe activation request from MS 910. SGSN 924 then initiates a DNS queryto learn which GGSN 932 has access to the UPS.com APN. The DNS query issent to a DNS server within core network 906, such as DNS server 930,which is provisioned to map to one or more GGSNs in core network 906.Based on the APN, the mapped GGSN 932 can access requested corporatenetwork 940. SGSN 924 then sends to GGSN 932 a Create PDP ContextRequest message that contains necessary information. GGSN 932 sends aCreate PDP Context Response message to SGSN 924, which then sends anActivate PDP Context Accept message to MS 910.

Once activated, data packets of the call made by MS 910 can then gothrough RAN 904, core network 906, and interconnect network 908, in aparticular FES/Internet 936 and firewall 1038, to reach corporatenetwork 940.

FIG. 10 illustrates a block diagram of an example PLMN architecture thatmay be replaced by a telecommunications system. In FIG. 10, solid linesmay represent user traffic signals, and dashed lines may representsupport signaling. MS 1002 is the physical equipment used by the PLMNsubscriber. For example, drone 102, network device 300, the like, or anycombination thereof may serve as MS 1002. MS 1002 may be one of, but notlimited to, a cellular telephone, a cellular telephone in combinationwith another electronic device or any other wireless mobilecommunication device.

MS 1002 may communicate wirelessly with BSS 1004. BSS 1004 contains BSC1006 and a BTS 1008. BSS 1004 may include a single BSC 1006/BTS 1008pair (base station) or a system of BSC/BTS pairs that are part of alarger network. BSS 1004 is responsible for communicating with MS 1002and may support one or more cells. BSS 1004 is responsible for handlingcellular traffic and signaling between MS 1002 and a core network 1010.Typically, BSS 1004 performs functions that include, but are not limitedto, digital conversion of speech channels, allocation of channels tomobile devices, paging, or transmission/reception of cellular signals.

Additionally, MS 1002 may communicate wirelessly with RNS 1012. RNS 1012contains a Radio Network Controller (RNC) 1014 and one or more Nodes B1016. RNS 1012 may support one or more cells. RNS 1012 may also includeone or more RNC 1014/Node B 1016 pairs or alternatively a single RNC1014 may manage multiple Nodes B 1016. RNS 1012 is responsible forcommunicating with MS 1002 in its geographically defined area. RNC 1014is responsible for controlling Nodes B 1016 that are connected to it andis a control element in a UMTS radio access network. RNC 1014 performsfunctions such as, but not limited to, load control, packet scheduling,handover control, security functions, or controlling MS 1002 access tocore network 1010.

An E-UTRA Network (E-UTRAN) 1018 is a RAN that provides wireless datacommunications for MS 1002 and UE 1024. E-UTRAN 1018 provides higherdata rates than traditional UMTS. It is part of the LTE upgrade formobile networks, and later releases meet the requirements of theInternational Mobile Telecommunications (IMT) Advanced and are commonlyknown as a 4G networks. E-UTRAN 1018 may include of series of logicalnetwork components such as E-UTRAN Node B (eNB) 1020 and E-UTRAN Node B(eNB) 1022. E-UTRAN 1018 may contain one or more eNBs. User equipment(UE) 1024 may be any mobile device capable of connecting to E-UTRAN 1018including, but not limited to, a personal computer, laptop, mobiledevice, wireless router, or other device capable of wirelessconnectivity to E-UTRAN 1018. The improved performance of the E-UTRAN1018 relative to a typical UMTS network allows for increased bandwidth,spectral efficiency, and functionality including, but not limited to,voice, high-speed applications, large data transfer or IPTV, while stillallowing for full mobility.

Typically MS 1002 may communicate with any or all of BSS 1004, RNS 1012,or E-UTRAN 1018. In a illustrative system, each of BSS 1004, RNS 1012,and E-UTRAN 1018 may provide MS 1002 with access to core network 1010.Core network 1010 may include of a series of devices that route data andcommunications between end users. Core network 1010 may provide networkservice functions to users in the circuit switched (CS) domain or thepacket switched (PS) domain. The CS domain refers to connections inwhich dedicated network resources are allocated at the time ofconnection establishment and then released when the connection isterminated. The PS domain refers to communications and data transfersthat make use of autonomous groupings of bits called packets. Eachpacket may be routed, manipulated, processed or handled independently ofall other packets in the PS domain and does not require dedicatednetwork resources.

The circuit-switched MGW function (CS-MGW) 1026 is part of core network1010, and interacts with VLR/MSC server 1028 and GMSC server 1030 inorder to facilitate core network 1010 resource control in the CS domain.Functions of CS-MGW 1026 include, but are not limited to, mediaconversion, bearer control, payload processing or other mobile networkprocessing such as handover or anchoring. CS-MGW 1026 may receiveconnections to MS 1002 through BSS 1004 or RNS 1012.

SGSN 1032 stores subscriber data regarding MS 1002 in order tofacilitate network functionality. SGSN 1032 may store subscriptioninformation such as, but not limited to, the IMSI, temporary identities,or PDP addresses. SGSN 1032 may also store location information such as,but not limited to, GGSN address for each GGSN 1034 where an active PDPexists. GGSN 1034 may implement a location register function to storesubscriber data it receives from SGSN 1032 such as subscription orlocation information.

Serving gateway (S-GW) 1036 is an interface which provides connectivitybetween E-UTRAN 1018 and core network 1010. Functions of S-GW 1036include, but are not limited to, packet routing, packet forwarding,transport level packet processing, or user plane mobility anchoring forinter-network mobility. PCRF 1038 uses information gathered from P-GW1036, as well as other sources, to make applicable policy and chargingdecisions related to data flows, network resources or other networkadministration functions. PDN gateway (PDN-GW) 1040 may provideuser-to-services connectivity functionality including, but not limitedto, GPRS/EPC network anchoring, bearer session anchoring and control, orIP address allocation for PS domain connections.

HSS 1042 is a database for user information and stores subscription dataregarding MS 1002 or UE 1024 for handling calls or data sessions.Networks may contain one HSS 1042 or more if additional resources arerequired. Example data stored by HSS 1042 include, but is not limitedto, user identification, numbering or addressing information, securityinformation, or location information. HSS 1042 may also provide call orsession establishment procedures in both the PS and CS domains.

VLR/MSC Server 1028 provides user location functionality. When MS 1002enters a new network location, it begins a registration procedure. A MSCserver for that location transfers the location information to the VLRfor the area. A VLR and MSC server may be located in the same computingenvironment, as is shown by VLR/MSC server 1028, or alternatively may belocated in separate computing environments. A VLR may contain, but isnot limited to, user information such as the IMSI, the Temporary MobileStation Identity (TMSI), the Local Mobile Station Identity (LMSI), thelast known location of the mobile station, or the SGSN where the mobilestation was previously registered. The MSC server may containinformation such as, but not limited to, procedures for MS 1002registration or procedures for handover of MS 1002 to a differentsection of core network 1010. GMSC server 1030 may serve as a connectionto alternate GMSC servers for other MSs in larger networks.

EIR 1044 is a logical element which may store the IMEI for MS 1002. Userequipment may be classified as either “white listed” or “black listed”depending on its status in the network. If MS 1002 is stolen and put touse by an unauthorized user, it may be registered as “black listed” inEIR 1044, preventing its use on the network. A MME 1046 is a controlnode which may track MS 1002 or UE 1024 if the devices are idle.Additional functionality may include the ability of MME 1046 to contactidle MS 1002 or UE 1024 if retransmission of a previous session isrequired.

As described herein, a telecommunications system wherein management andcontrol utilizing a software designed network (SDN) and a simple IP arebased, at least in part, on user equipment, may provide a wirelessmanagement and control framework that enables common wireless managementand control, such as mobility management, radio resource management,QoS, load balancing, etc., across many wireless technologies, e.g. LTE,Wi-Fi, and future 5G access technologies; decoupling the mobilitycontrol from data planes to let them evolve and scale independently;reducing network state maintained in the network based on user equipmenttypes to reduce network cost and allow massive scale; shortening cycletime and improving network upgradability; flexibility in creatingend-to-end services based on types of user equipment and applications,thus improve customer experience; or improving user equipment powerefficiency and battery life—especially for simple M2M devices—throughenhanced wireless management.

While examples of a telecommunications system in which emergency alertscan be processed and managed have been described in connection withvarious computing devices/processors, the underlying concepts may beapplied to any computing device, processor, or system capable offacilitating a telecommunications system. The various techniquesdescribed herein may be implemented in connection with hardware orsoftware or, where appropriate, with a combination of both. Thus, themethods and devices may take the form of program code (i.e.,instructions) embodied in concrete, tangible, storage media having aconcrete, tangible, physical structure. Examples of tangible storagemedia include floppy diskettes, CD-ROMs, DVDs, hard drives, or any othertangible machine-readable storage medium (computer-readable storagemedium). Thus, a computer-readable storage medium is not a signal. Acomputer-readable storage medium is not a transient signal. Further, acomputer-readable storage medium is not a propagating signal. Acomputer-readable storage medium as described herein is an article ofmanufacture. When the program code is loaded into and executed by amachine, such as a computer, the machine becomes an device fortelecommunications. In the case of program code execution onprogrammable computers, the computing device will generally include aprocessor, a storage medium readable by the processor (includingvolatile or nonvolatile memory or storage elements), at least one inputdevice, and at least one output device. The program(s) can beimplemented in assembly or machine language, if desired. The languagecan be a compiled or interpreted language, and may be combined withhardware implementations.

The methods and devices associated with a telecommunications system asdescribed herein also may be practiced via communications embodied inthe form of program code that is transmitted over some transmissionmedium, such as over electrical wiring or cabling, through fiber optics,or via any other form of transmission, wherein, when the program code isreceived and loaded into and executed by a machine, such as an EPROM, agate array, a programmable logic device (PLD), a client computer, or thelike, the machine becomes an device for implementing telecommunicationsas described herein. When implemented on a general-purpose processor,the program code combines with the processor to provide a unique devicethat operates to invoke the functionality of a telecommunicationssystem.

EXAMPLES Example 1

A system for predictive maintenance of at least one optical networkelement in an optical transport network comprising: a power monitor incommunication with the at least one optical network element, the powermonitor configured to selectively retrieve an actual power level fromthe optical network element; the power monitor being in communicationwith a data store having a specified power, level for each of the atleast one optical network element and an acceptable tolerance, whereinthe specified power level includes a low mark and a high mark defining aspecified power level range; wherein the power monitor compares theactual power level to the specified power level; and generates a signalif the actual power level is outside of the specified power level rangeby an amount greater than the acceptable tolerance.

Example 2

The system of example 1, wherein the signal includes a notice to repairor replace the at least one optical network element that is outside ofthe specified power level range.

Example 3

The system of example 1, wherein the power monitor is configured toselectively retrieve the actual power level at a first frequency,wherein upon detecting an actual power level within the specified rangebut outside of an operating range, the power monitor is configured toselectively retrieve the actual power level for the at least one opticalnetwork element with the actual power level outside of the operatingrange to a second frequency, wherein the second frequency is greaterthan the first frequency.

Example 4

The system of example 3, wherein the operating range is 70% of thespecified range.

Example 5

The system of example 3, wherein the operating range is 90% of thespecified range.

Example 6

The system of example 1, wherein the power monitor is configured tostore the actual power level obtained during each selected retrieval ina memory, wherein the power monitor is configured to analyze a trenddefined by comparing the actual power level in the memory as a functionof time, and wherein upon detecting a degradation in performance withinthe trend, the power monitor is configured to perform at least one ofincreasing a frequency of selectively retrieval of the power level orgenerating a signal to repair or replace the at least one opticalnetwork element having the degradation in performance within the trend.

Example 7

The system of example 1, wherein the acceptable tolerance is plus orminus 10% of the low mark and high mark.

Example 8

The system of example 1, wherein the power monitor is configured toretrieve the actual power level according to a schedule, wherein thepower monitor is configured to determine the schedule based in part uponnetwork load and retrieve the actual power level during a non-peaknetwork load time period.

Example 9

The system of example 8, wherein the schedule includes a first frequencyon which the power monitor is configured to retrieve the actual powerlevel, and wherein the power monitor is configured to increase the firstfrequency upon detecting the actual power level is within outside orinside of the specified power range by an acceptable tolerance.

Example 10

The system of example 8, wherein the acceptable tolerance is 30%

Example 11

The system of example 8, wherein the acceptable tolerance is 10%.

Example 12

A system for predictive maintenance of an optical transport network, thesystem comprising: plural optical network elements in the opticaltransport network, each optical network element operating at an actualpower level; at least one data store having a specified power level foreach optical network element, wherein the specified power level includesa low mark and a high mark defining a specified power level range; apower monitor in communication with the data store and the opticalnetwork elements, the power monitor configured to selectivelycommunicate with each optical network element according to a schedule,to retrieve the actual power level and store the actual power level in amemory, the power monitor is further configured to compare the actualpower level to the specified power level, and wherein the power monitoris configured to generate a first signal upon detecting that the actualpower level for at least one of the plural optical network elements iswithin an acceptable tolerance of the low mark or high mark, and whereinthe power monitor is configured to generate a second signal upondetecting the actual power level for at least one of the plural opticalnetwork elements is outside of specified power level range.

Example 13

The system of example 12, wherein the schedule includes a retrievalfrequency, and wherein the first signal generated by the power monitoris configured to increase the retrieval frequency for the at least oneof the plural optical network elements operating within an acceptabletolerance of the specified power level range.

Example 14

The system of example 12, wherein the second signal is a notice torepair or replace the one of the plural optical network elementsoperating outside of the specified range.

Example 15

The system of example 12, wherein the power monitor is configured toanalyze a trend defined by comparing the actual power level for each ofthe plural optical network elements in the memory as a function of time,and wherein upon detecting a degradation in performance within thetrend, the power monitor is configured to perform at least one ofincreasing a frequency of selectively retrieval of the power level orgenerating a signal to repair or replace the at least one opticalnetwork element having the degradation in performance within the trend.

Example 16

The system of example 12, wherein the acceptable tolerance is plus orminus 30%.

Example 17

The system of example 12, wherein the acceptable tolerance is plus orminus 10%.

Example 18

The system of example 12, wherein the power monitor is configured todefine an operating range that is less than the specified power level,and wherein the power monitor is configured to generate the secondsignal if the actual power level of at least one of the plural opticalnetwork elements is outside of the operating range.

Example 19

The system of example 12, wherein at least one of the plural opticalnetwork elements reside in at least one of a first level network, asecond level network and a third level network.

Example 20

The system of example 12, wherein the specified power level includes anoptical power transmit value and an optical power receive value for thenetwork element; and wherein upon detecting an optical power receivevalue outside of the specified range, power monitor retrieves theoptical power transmit value for the network element; communicates withat least a second network element connected to the network element by aconnection and retrieves an optical power transmit value for the atleast second network element; and wherein the power monitor determinesif the optical power transmit value for the network element is withinthe specified range and if the optical power transmit value for thesecond network element is with a specified range for the second networkelement; and wherein if at least one of optical power transmit valuesfor the network element and the second network element are out of thespecified range, power monitor recommends repair of at least one of thenetwork element and the at least one second network element; and if thepower monitor determines that the network element and the at least onesecond network element have optical transmit values within the specifiedrange, the power monitor recommends at least one of repair andreplacement of the connection.

Example 21

The system of example 3, wherein the operating range includes a vendorvalue stored in the data store and accessible by the power monitor.

Example 22

The system of example 6, wherein the power monitor is configured toupdate the vendor value in response to at least one of a passage of timeand an input of an updated operating range.

1. A system for predictive maintenance of at least one optical networkelement in an optical transport network comprising: a power monitor incommunication with the at least one optical network element, the powermonitor configured to selectively retrieve an actual power level fromthe optical network element; the power monitor being in communicationwith a data store having a specified power level for each of the atleast one optical network element and an acceptable tolerance, whereinthe specified power level includes a low mark and a high mark defining aspecified power level range; wherein the power monitor compares theactual power level to the specified power level; and generates a signalif the actual power level is outside of the specified power level rangeby an amount greater than the acceptable tolerance; wherein the powermonitor is configured to store the actual power level obtained duringeach selected retrieval in a memory, wherein the power monitor isconfigured to analyze a trend defined by comparing the actual powerlevel in the memory as a function of time, and wherein upon detecting adegradation in performance within the trend, the power monitor isconfigured to perform at least one of increasing a frequency ofselectively retrieval of the power level or generating a signal torepair or replace the at least one optical network element having thedegradation in performance within the trend.
 2. The system of claim 1,wherein the signal includes a notice to repair or replace the at leastone optical network element that is outside of the specified power levelrange.
 3. The system of claim 1, wherein the power monitor is configuredto selectively retrieve the actual power level at a first frequency,wherein upon detecting an actual power level within the specified rangebut outside of an operating range, the power monitor is configured toselectively retrieve the actual power level for the at least one opticalnetwork element with the actual power level outside of the operatingrange to a second frequency, wherein the second frequency is greaterthan the first frequency.
 4. The system of claim 3, wherein theoperating range is 70% of the specified range.
 5. The system of claim 3,wherein the operating range is 90% of the specified range.
 6. (canceled)7. The system of claim 1, wherein the acceptable tolerance is plus orminus 10% of the low mark and high mark.
 8. A system for predictivemaintenance of at least one optical network element in an opticaltransport network comprising: a power monitor in communication with theat least one optical network element, the power monitor configured toselectively retrieve an actual power level from the optical networkelement; the power monitor being in communication with a data storehaving a specified power level for each of the at least one opticalnetwork element and an acceptable tolerance, wherein the specified powerlevel includes a low mark and a high mark defining a specified powerlevel range; wherein the power monitor compares the actual power levelto the specified power level; and generates a signal if the actual powerlevel is outside of the specified power level range by an amount greaterthan the acceptable tolerance; wherein the power monitor is configuredto retrieve the actual power level according to a schedule, wherein thepower monitor is configured to determine the schedule based in part uponnetwork load and retrieve the actual power level during a non-peaknetwork load time period.
 9. The system of claim 8, wherein the scheduleincludes a first frequency on which the power monitor is configured toretrieve the actual power level, and wherein the power monitor isconfigured to increase the first frequency upon detecting the actualpower level is within outside or inside of the specified power range byan acceptable tolerance.
 10. The system of claim 8, wherein theacceptable tolerance is 30%.
 11. The system of claim 8, wherein theacceptable tolerance is 10%.
 12. A system for predictive maintenance ofan optical transport network, the system comprising: plural opticalnetwork elements in the optical transport network, each optical networkelement operating at an actual power level; at least one data storehaving a specified power level for each optical network element, whereinthe specified power level includes a low mark and a high mark defining aspecified power level range; a power monitor in communication with thedata store and the optical network elements, the power monitorconfigured to selectively communicate with each optical network elementaccording to a schedule, to retrieve the actual power level and storethe actual power level in a memory, the power monitor is furtherconfigured to compare the actual power level to the specified powerlevel, and wherein the power monitor is configured to generate a firstsignal upon detecting that the actual power level for at least one ofthe plural optical network elements is within an acceptable tolerance ofthe low mark or high mark, and wherein the power monitor is configuredto generate a second signal upon detecting the actual power level for atleast one of the plural optical network elements is outside of specifiedpower level range.
 13. The system of claim 12, wherein the scheduleincludes a retrieval frequency, and wherein the first signal generatedby the power monitor is configured to increase the retrieval frequencyfor the at least one of the plural optical network elements operatingwithin an acceptable tolerance of the specified power level range. 14.The system of claim 12, wherein the second signal is a notice to repairor replace the one of the plural optical network elements operatingoutside of the specified range.
 15. The system of claim 12, wherein thepower monitor is configured to analyze a trend defined by comparing theactual power level for each of the plural optical network elements inthe memory as a function of time, and wherein upon detecting adegradation in performance within the trend, the power monitor isconfigured to perform at least one of increasing a frequency ofselectively retrieval of the power level or generating a signal torepair or replace the at least one optical network element having thedegradation in performance within the trend.
 16. The system of claim 12,wherein the acceptable tolerance is plus or minus 30%.
 17. The system ofclaim 12, wherein the acceptable tolerance is plus or minus 10%.
 18. Thesystem of claim 12, wherein the power monitor is configured to define anoperating range that is less than the specified power level, and whereinthe power monitor is configured to generate the second signal if theactual power level of at least one of the plural optical networkelements is outside of the operating range.
 19. The system of claim 12,wherein at least one of the plural optical network elements reside in atleast one of a first level network, a second level network and a thirdlevel network.
 20. The system of claim 12, wherein the specified powerlevel includes an optical power transmit value and an optical powerreceive value for the network element; and wherein upon detecting anoptical power receive value outside of the specified range, powermonitor retrieves the optical power transmit value for the networkelement; communicates with at least a second network element connectedto the network element by a connection and retrieves an optical powertransmit value for the at least second network element; and wherein thepower monitor determines if the optical power transmit value for thenetwork element is within the specified range and if the optical powertransmit value for the second network element is with a specified rangefor the second network element; and wherein if at least one of opticalpower transmit values for the network element and the second networkelement are out of the specified range, power monitor recommends repairof at least one of the network element and the at least one secondnetwork element; and if the power monitor determines that the networkelement and the at least one second network element have opticaltransmit values within the specified range, the power monitor recommendsat least one of repair and replacement of the connection.